Summary

Rename internal crates to the tracker-deployer namespace before first crates.io publication, and propagate the new names through workspace dependencies, workflows, tests, docs, and examples.

Renames

• torrust-deployer-types -> torrust-tracker-deployer-types
• torrust-dependency-installer -> torrust-tracker-deployer-dependency-installer

Why

No crate has been published yet, so this is the safest point to align crate names with the repository/project namespace and avoid long-term migration overhead.

Scope

• Cargo manifests and dependency references
• publish workflow crate names and checks
• Rust imports/usages where needed
• docs/examples/help text references

Validation

• pre-commit checks run locally before branch handoff
• PR CI runs the full workflow matrix before merge

Follow-up

After merge, re-run the release branch workflow and verify crates.io publication with updated token permissions in the crates-io environment.